home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Varsity Update 1998 August
/
SGI Varsity Update 1998 August.iso
/
dist
/
dist6.4
/
pvm.idb
/
usr
/
share
/
catman
/
u_man
/
cat1
/
pvmd3.z
/
pvmd3
Wrap
Text File
|
1998-07-29
|
18KB
|
342 lines
PVMD3(1) Last changed: 5-8-98
NNAAMMEE
ppvvmmdd33 - Starts the Parallel Virtual Machine (PVM) daemon
SSYYNNOOPPSSIISS
ppvvmmdd33 [_o_p_t_i_o_n_s] [_h_o_s_t_f_i_l_e]
IIMMPPLLEEMMEENNTTAATTIIOONN
UNICOS, UNICOS/mk, and IRIX systems
Cray Research and Silicon Graphics offer two release packages that
include PVM libraries; they are referred to as the CRAY T3D version
and the MPT version. For more information about the MPT version, see
the _M_e_s_s_a_g_e _P_a_s_s_i_n_g _T_o_o_l_k_i_t: _P_V_M _P_r_o_g_r_a_m_m_e_r'_s _M_a_n_u_a_l, publication SR-
2196.
This command is not available in the following release packages:
CRAY T3D version
MPT version in stand-alone mode
DDEESSCCRRIIPPTTIIOONN
The ppvvmmdd33 command starts the Parallel Virtual Machine (PVM) daemon.
This user-level daemon process allows coordination between systems in
a PVM virtual machine. One daemon must run on each system. These
daemons provide the communication and process control functions needed
by PVM processes.
You can start the local daemon manually with a host file option that
automatically starts the remote daemons. It can be started by a shell
script, $$PPVVMM__RROOOOTT//lliibb//ppvvmmdd, or by starting the executable file
directly, $$PPVVMM__RROOOOTT//lliibb//$$PPVVMM__AARRCCHH//ppvvmmdd33. You can also start the local
and remote daemons on the PVM console by using the ppvvmm(1) command.
On UNICOS and UNICOS/mk systems, use of MPT requires the Cray
Programming Environment 3.0 releases or later, and requires use of
Modules software. Use the Modules software package to install both
the Programming Environment and MPT. To use MPT software, load the
mmpptt module in addition to loading the Programming Environment module.
For information on using modules, see _I_n_s_t_a_l_l_i_n_g _P_r_o_g_r_a_m_m_i_n_g
_E_n_v_i_r_o_n_m_e_n_t _P_r_o_d_u_c_t_s, publication SG-5191, or if the Programming
Environment has already been installed on your system, see the online
ASCII file, //oopptt//ccttll//ddoocc//RREEAADDMMEE. After you have initialized modules,
to access the MPT software, enter the following command:
module load mpt
When you use the MPT version of PVM, $$PPVVMM__RROOOOTT and $$PPVVMM__AARRCCHH are set
automatically for you when the mmpptt module is loaded.
On IRIX systems, the use of Modules software is optional. However,
IRIX users can set the following environment variables:
* If PVM is installed in a standard location, set PPVVMM__RROOOOTT to
//uussrr//aarrrraayy//PPVVMM. Otherwise, use the appropriate value.
* Set PPVVMM__AARRCCHH to the appropriate architecture type (see the
ppvvmm__iinnttrroo(1) man page).
* Add $$PPVVMM__RROOOOTT//lliibb and $$PPVVMM__RROOOOTT//bbiinn//$$PPVVMM__AARRCCHH to the PPAATTHH
environment variable.
Entering the hhaalltt command on the PVM console is the preferred method
of stopping every daemon. (For information on using the PVM console,
see the ppvvmm(1) command.) This command kills all PVM tasks, all remote
daemons, the local daemon, and finally the console itself. If the
master daemon is killed manually, it sends a SSIIGGTTEERRMM signal to allow
it to kill the remote daemon and to clean up various files.
If the daemon is killed in a manner that leaves behind the UNICOS or
UNICOS/mk //ttmmpp//ppvvmmdd.._u_i_d file or the IRIX //ttmmpp//ppvvmmdd.._u_i_d.._v_m_i_d ffiillee oonn
oonnee oorr mmoorree ssyysstteemmss,, ddeelleettee tthhee ffiillee.. IIff tthhee ffiillee rreemmaaiinnss,, iitt ccaann
pprreevveenntt PPVVMM ffrroomm rreessttaarrttiinngg oonn tthhaatt ssyysstteemm..
The ppvvmmdd33 command accepts the following options and operand:
_o_p_t_i_o_n_s Specifies one or more of the following options:
--dd_m_a_s_k Sets the PVM daemon debug mask. You can use this
option to debug the ppvvmmdd33 command (not application
programs).
The _m_a_s_k variable is a hexadecimal number that is
the sum of the following bits:
1 Packet routing
2 Message routing and entry points
4 Task state
8 Slave pvmd startup
10 Host table updates
20 Select loop (below packet layer)
40 IP network
80 Multiprocessor nodes
100 Resource manager interface
200 Application (messages with no destination,
and so on)
400 Shared memory operations
800 Semaphones
1000 Locks
--hh Specifies automatic creation of the host file by
using NQE. If _h_o_s_t_f_i_l_e is also specified, the
options from that host file are used but the host
is started only if NQE includes it in its list of
available hosts. This option is not supported on
UNICOS/mk or IRIX systems.
--nn_n_a_m_e Specifies an alternate host name for the master
daemon to use. You must use the same name to
identify the configuration information in the host
file.
The following options, which the master daemon uses when
starting remote systems, are available to programmers
writing host starter applications. (See the
ppvvmm__rreegg__hhoosstteerr(3) function.)
--ss Starts the PVM daemon in remote mode. You cannot use a
host file and must supply the following parameters:
_m_a_s_t_e_r _p_v_m_d _i_n_d_e_x, _m_a_s_t_e_r _I_P, _m_a_s_t_e_r _M_T_U, _r_e_m_o_t_e _p_v_m_d
_i_n_d_e_x, and _r_e_m_o_t_e _I_P.
--SS Starts the PVM daemon in remote mode, but the remote
PVM daemon does not wait for its ssttddiinn file to be
closed after printing its parameters. Use this option
for manual startup.
--ff Ensures that the remote PVM daemon does not fork after
configuration. This option is useful if the remote
daemon is to be controlled or monitored by some
process.
_h_o_s_t_f_i_l_e Specifies the host file that contains the names of the
systems in the virtual machine. For host file and option
information, see the "Host File Format" and "Host File
Options" subsections.
HHoosstt FFiillee FFoorrmmaatt
Each system that the daemon should include in the virtual machine must
have an entry in the host file, with the exception of the local
daemon. The machine that runs the local daemon is always included in
the virtual machine. To specify options for the local daemon, its
name must be specified in the host file with the appropriate options.
The name that identifies the local machine should be the name returned
by the hhoossttnnaammee command on your system. Alternatively, the --nn option
can be used to specify an alternate host name to be used in the host
file. To use a particular network interface, use the --iipp option to
specify the interface name.
If NQE is available, automatic creation of the list of hosts in the
virtual machine can be requested by using the --hh option. The policy
called PVM is used to request a list of hosts. For more information
on policies, see the _N_Q_E _U_s_e_r'_s _G_u_i_d_e, publication SG-2148.
If a host file is specified with the --hh option, the options are read,
but only the hosts returned from NQE are started as part of the
virtual machine. If default options are acceptable to the user, it is
not necessary to specify a host file.
The following example shows the format of a host file:
# my first host file
gust.cray.com
fred dx=$PVM_ROOT/lib/$PVM_ARCH/pvmd3
wilma ep=/cray/uss/ptmp/mylogin/text dx=$PVM_ROOT/lib/$PVM_ARCH/pvmd3
This sample file contains the names of the three systems in the
virtual machine. Lines beginning with a # symbol, optionally preceded
by white space, are ignored.
The master daemon (master system or host) for a group is started by
hand on the local system, and it starts slaves on each of the
remaining systems using the remote shell rreemmsshh(1) (on UNICOS or
UNICOS/mk systems) or aarrsshheellll(1) (on IRIX systems with Array Services
installed) or rrsshh(1) (on IRIX systems without Array Services
installed). The master system can have an entry in the host file,
which is identified with the name returned from the hhoossttnnaammee command
or the name specified with the --nn option. Host names cannot be
numeric (IP) addresses, because they are passed to rrsshh() or rreemmsshh,
which usually do not accept addresses.
You can change the default options in the host file by adding a line
with an asterisk in the first field followed by the options, as shown
in the following example:
** lloo==aaffrriieenndd ssoo==ppww
This sets new default values for lloo and ssoo==ppww for the systems in the
remainder of the host file or until the option is reset by another
line with an asterisk.
A dollar sign ( $ ) in an option introduces an environment variable
name, for example, $$PPVVMM__AARRCCHH. Names are expanded from environment
variables by each PVM daemon.
Your application may use the ppvvmm__aaddddhhoossttss(3) function to add a new
system to the virtual machine, but it may be necessary to define
options such as ddxx or eepp for this system. If you prefix the
appropriate host file line with an ampersand (&), the PVM daemon will
save the information but will not start a daemon on that system until
you call ppvvmm__aaddddhhoossttss(3), as shown in the following example:
& poplar dx=$PVM_ROOT/lib/$PVM_ARCH/pvmd3
This host file entry will not start a daemon on ppooppllaarr, but if a
request is received later, PVM will use the indicated path for the PVM
daemon.
HHoosstt FFiillee OOppttiioonnss
For complex configurations, you can specify the following options
after any system name in the host file.
bbxx==_d_p_a_t_h Specifies the debugger path. You can also set this path
by using the PPVVMM__DDEEBBUUGGGGEERR environment variable. The
default is $$PPVVMM__RROOOOTT//lliibb//ddeebbuuggggeerr.
ddxx==_l_o_c Specifies a location for the PVM daemon other than the
default, $$PPVVMM__RROOOOTT//lliibb//ppvvmmdd. This option is useful in
debugging new versions of PVM. _l_o_c may be a simple file
name, an absolute path name, or a path relative to the
user's home directory on the remote system. When the MPT
version is installed on UNICOS or IRIX systems, the ppvvmmdd33
command is installed in $$PPVVMM__RROOOOTT//lliibb//$$PPVVMM__AARRCCHH//ppvvmmdd33 and
the start-up script is installed in //$$PPVVMM__RROOOOTT//lliibb//ppvvmmdd.
You might want to set ddxx to either of these paths in host
file entries for these systems.
eepp==_p_a_t_h_s Specifies a series of paths to search for the requested
files to spawn on the system. A percent sign (%) in the
path expands to the architecture of the remote system.
Multiple paths are separated by a colon. The default is
$$HHOOMMEE//ppvvmm33//bbiinn//$$PPVVMM__AARRCCHH:: $$PPVVMM__RROOOOTT//bbiinn//$$PPVVMM__AARRCCHH.
lloo==_u_s_e_r_i_d Specifies an alternate login name for the system. The
default is the login name on the master system.
ssoo==mmss Causes the master PVM daemon to request that you manually
start a PVM daemon on a remote system when the rrsshh or
aarrsshheellll (or rreemmsshh) and rreexxeecc(3C) network services are
disabled, but IP connectivity exists. The default is
false. (This option is rarely used.) You cannot start
the master system from the PVM console or background when
you are using this option.
ssoo==ppww Causes PVM to prompt for a password for the remote system.
This option is useful when you have a different login name
and password on a remote system. The master host prompts
you for your password as follows:
Password (honk.cs.utk.edu:manchek):
Enter your password for the remote system. Startup will
then continue as normal. You cannot start the master host
from the PVM console or background when you are using this
option. The PVM daemon uses the rreexxeecc(3C) function
instead of rrsshh or rreemmsshh or aarrsshheellll.
sspp==_v_a_l_u_e Specifies the relative computational speed of the system
compared to other system in the configuration. _v_a_l_u_e is
an integer in the range 1 through 1,000,000. The default
is 1000. (This option currently has no effect on PVM
operation.)
wwdd==_p_a_t_h Specifies a working directory in which all spawned tasks
on the host will execute. The default is $$HHOOMMEE.
iipp==_n_e_t_w_o_r_k__n_a_m_e
Specifies the network name to be used for communication.
The default is determined by the network routing, as shown
by the nneettssttaatt --ii command. You can use this option to
specify HIPPI or another specific device.
EEXXAAMMPPLLEESS
The following examples illustrate how to use options in a host file:
Example 1:
# host file for testing on various platforms
fonebone
refuge
# installed in /usr/local/here
sigi.cs dx=$PVM_ROOT/lib/pvmd
# borrowed accts, "guest", don't trust fonebone
* lo=guest so=pw
sn666.jrandom.com
cubie.misc.edu
# really painful one, must start it by hand and share a homedir
igor.firewall.com lo=guest2 so=ms ep=bob/pvm3/bin/%
Example 2:
# host file for using hippi network.
# The hosts are normally referred to as gust and cool.
# NOTE: Do not use the -n option to specify gust-hippi.
# This causes a configuration with 3 machines named
# gust, gust-hippi, and cool. Since gust-hippi doesn't
# appear in the host file, it has default options
# associated with it. This can be VERY confusing.
gust ip=gust-hippi
cool ip=cool-hippi
FFIILLEESS
//ttmmpp//ppvvmmdd.._u_i_d PVM daemon file, containing socket
information
//ttmmpp//ppvvmmll.._u_i_d PVM log file, containing text written to
the ssttddoouutt and ssttddeerrrr files
$$PPVVMM__RROOOOTT//lliibb//ppvvmmdd PVM daemon start-up script
$$PPVVMM__RROOOOTT//lliibb//$$PPVVMM__AARRCCHH//ppvvmmdd33 PVM daemon executable file
$$PPVVMM__RROOOOTT//lliibb//ddeebbuuggggeerr Debugger script
SSEEEE AALLSSOO
ppvvmm(1), ppvvmm__iinnttrroo(1), ppvvmm__aaddddhhoossttss(3), ppvvmm__rreegg__hhoosstteerr(3)
rreemmsshh(1B) in the _U_N_I_C_O_S _U_s_e_r _C_o_m_m_a_n_d_s _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l, publication SR
-2011. (On other systems, you may want to use rrsshh() or rreemmsshh(),
whichever is the appropriate remote shell for your system.)
_N_Q_E _U_s_e_r'_s _G_u_i_d_e, publication SG-2148
_M_e_s_s_a_g_e _P_a_s_s_i_n_g _T_o_o_l_k_i_t: _P_V_M _P_r_o_g_r_a_m_m_e_r'_s _M_a_n_u_a_l, publication SR-2196
This man page is available only online.